Release 10.1A: OpenEdge Development:
ADM Reference

RunDOOptions

Comma-separated list of options that determine how Data Objects are run from constructObject. The available options are:

dynamicOnly — Run the Dynamics client proxy SDO specified in the DynamicSDOProcedure property. By default, this is adm2/dyndata.w. When you select this option, no other version of the data object will be run.
sourceSearch — Search for and run the actual source object. If it is not available or the required databases are not connected, use the clientOnly option.
clientOnly — Do not locate or run the actual object file (sdo-name.w). Instead, locate the static client file (*_cl.w) and run it. If this file is not available, run the Dynamics client proxy.
StaticClientOnly — This option is similar to the clientOnly option, except that the Dynamics client proxy (dyndata.w) is not run if the static client (*_cl.w) is not available. This option takes precedence over the dynamicOnly option when there is a conflict.
Data type: CHARACTER
Notes:
Read and Write.
The StaticClientOnly option is useful in a WebClient session when you do not want to run the Dynamics client proxy and the static client does not reside on the client. Under those conditions, selecting the StaticClientOnly option forces an automatic WebClient download of the static client (*_cl).
If dynamicOnly, clientOnly, or both of these options are specified, the Data Object must have an AppServer partition defined. If an AppServer partition is not defined, and dynamicOnly, clientOnly, or both options are specified, you will experience the same errors that occur when the Data Object is running on an AppServer that has not been started.
To run source code when no rcode is found, you must customized containr.p by setting RunDOOptions to sourceSearch in constructObject.